fix(ingest): fix extra forward slash for looker url generation#16274
Merged
kevinkarchacryl merged 1 commit intomasterfrom Feb 20, 2026
Merged
fix(ingest): fix extra forward slash for looker url generation#16274kevinkarchacryl merged 1 commit intomasterfrom
kevinkarchacryl merged 1 commit intomasterfrom
Conversation
Contributor
|
Linear: ING-1677 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
treff7es
approved these changes
Feb 20, 2026
askumar27
pushed a commit
to acryldata/datahub
that referenced
this pull request
Feb 23, 2026
neildsouth
pushed a commit
to National-Digital-Twin/ndt-data-catalogue
that referenced
this pull request
Feb 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It's possible that links for Looker will have two forward slashes in the URL like "{base_url}//looks/{self.look_id}" instead of "{base_url}/looks/{self.look_id}". This fixes the issue in several places in looker_common.